Add model registry continuity fixtures#2135
Open
DENGXUELIN wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
/claim #1331
What changed
Adds fixture-backed registry availability and rollback continuity gates to
model-supply-chain.MODEL-RET-01throughMODEL-RET-08for immutable internal mirrors, retention/deletion controls, complete artifact sets, adapter/base/tokenizer/config binding, license/access snapshots, immutable rollback copies, clean-environment rebuild drills, and upstream deletion/gating ownership.Why this PR
Existing PR #1353 is a useful
SKILL.md-only implementation. This PR is intentionally fixture-backed and adds concrete skill-local examples so future reviews can distinguish integrity pinning from operational continuity when public registries remove, gate, rename, or evict model artifacts.Validation
git diff --check origin/main...HEADgit merge-tree --write-tree origin/main HEADmodel-supply-chain/SKILL.mdversion: "1.0.1",Registry Availability and Rollback Continuity,Continuity evidence gates,MODEL-RET-01throughMODEL-RET-08,Registry Continuity Evidence output,Internal Mirror,Rollback Copy, andTreating revision pins as availability guaranteesHEAD^{tree}after Git HTTPS push failed and the branch was created through the GitHub Git Data APIBounty tier
Requesting Improver Moderate ($100) if accepted. This adds local benign/vulnerable fixtures in addition to the registry-retention and rollback-continuity guidance requested by the issue.